Methods and apparatus to manage conference calls

ABSTRACT

Methods and apparatus to manage conference calls are described. An example method includes enabling, via a logic circuit, a first one of participants of a conference call to request an adjustment of a volume of a current speaker different than the first participant; and in response to a request from the first participant, adjusting, via the logic circuit, an amplification setting associated with the current speaker in a preference file associated with the first participant.

RELATED APPLICATION

This patent arises from a continuation of U.S. patent application Ser.No. 13/780,816, filed Feb. 28, 2013, now U.S. Pat. No. 9,019,868, whichis a continuation of U.S. patent application Ser. No. 12/039,575, filedFeb. 28, 2008, now U.S. Pat. No. 8,411,835. U.S. patent application Ser.No. 13/780,816 and U.S. patent application Ser. No. 12/039,575 arehereby incorporated herein by reference in their entireties.

TECHNICAL FIELD

The present disclosure relates generally to telecommunications, and moreparticularly, to methods and apparatus to manage conference calls.

BACKGROUND

Conference calls allow a plurality of participants to communicatesimultaneously from multiple remote locations. The number ofparticipants on a conference call can range from three into thehundreds.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustration of an example Internet protocol (IP)based communication system to manage a conference call.

FIG. 2 illustrates an example implementation of the conference callmanager of FIG. 1.

FIGS. 3A-C is a flowchart representation of machine readableinstructions that may be executed to implement the system of FIG. 1.

FIG. 4 illustrates an example user interface to be displayed to a userduring a conference call.

FIG. 5 is a schematic illustration of an example processor platformwhich may execute the example machine readable instructions of FIGS. 3A,3B, and/or 3C to implement the example system of FIG. 1.

DETAILED DESCRIPTION

During some conference calls, participants are not familiar with eachother and may be unaware of the identity of the current speaker, leadingto undesirable interruptions and general confusion. Further, varyingvolume levels from different participants may require recurringadjustments of the volume settings of a communication device. The volumeat which a participant is heard may be dictated by a device (e.g., acell phone or speakerphone) used to make the call, the environment(e.g., an office, car, or crowded place) from which the participant iscalling, or a tendency to speak loudly or softly in comparison with theother participants of the conference call. Such factors may cause anaudio signal from one participant to be transmitted at a blaring volumelevel, while another participant may be hardly audible.

Methods and apparatus to manage conference calls will now be disclosed.As described in further detail herein, an example method of managing aconference call includes enabling a participant of the conference callto request an adjustment of a volume of a current speaker and, inresponse to such a request, adjusting an amplification settingassociated with the current speaker in a preference file correspondingto the requesting participant. The adjustment made to the amplificationsetting is stored (e.g., temporarily for the duration of the conferencecall or permanently for future conference calls) to avoid the need tocontinuously adjust a volume setting of the communication device used toparticipate in the conference call (e.g., a speakerphone or cellulartelephone).

Another example method of managing a conference call includes, detectingan attempt of a first participant to interrupt a second participanthaving a higher priority value. In response to the attempt, the audiosignal of the first participant is blocked and an identifier associatedwith the first participant is placed in a queue. The queue may includeother participants who had attempted to interrupt a higher rankedparticipant. The audio signal of the first participant may later beunblocked according to the organization of the queue. This examplemethod enables participants to avoid undesired and perhaps damaginginterruptions of important participants (e.g., a supervisor, customer,or moderator).

FIG. 1 is a schematic illustration of an example Internet protocol (IP)based communication system 100 capable of implementing the methods andapparatus to manage conference calls described herein. To enable aplurality of participants to join a conference call and to manage one ormore policies thereof, the example communication system 100 of FIG. 1includes a conference call manager 102, which is described in greaterdetail below in connection with FIG. 2. In the illustrated examplesystem 100 of FIG. 1, a conference call participant employs aVoIP-enabled device to dial a call-in telephone number, which may bedialed by all potential participants and is, thus, referred to as a“conference call telephone number” or, “call-in telephone number” ormore succinctly, a “common telephone number.” The conference callmanager 102 may be assigned the common telephone number, a web address(e.g., HTTP), and/or an IP address. Further, the example conference callmanager 102 of FIG. 1 includes or is communicatively coupled to aconference bridge 104 to permit the participants at the same and/ordiverse locations to be connected. The example conference bridge 104 ofFIG. 1 amplifies and/or balances audio signal levels (e.g., via acommunication interface operatively coupled to one or more mixers and/orbuffers, a codec, and a processor) for each of the callers so that everyparticipant can hear and/or speak to each other during the conferencecall. As described in further detail below, the example conference callmanager 102 of FIG. 1 enables participants to control or customize(e.g., via an instruction sent to the conference call manager 102 via awebpage) the amplification and/or balancing of the audio signal levelsassociated with individual participants.

To enable users to place and/or receive a voice over Internet Protocol(VoIP) based communication (e.g., a telephone service, Internet service,data service, messaging service, instant messaging service, electronicmail (e-mail) service, chat service, video service, audio service,gaming service, etc.), the example communication system 100 of FIG. 1includes one or more VoIP-enabled devices, four of which are illustratedin FIG. 1 with reference numerals 108, 110, 112, and 114. Specifically,the illustrated example of FIG. 1 includes a wireless VoIP device 108(e.g., a wireless-fidelity (a.k.a. Wi-Fi) IP phone), any corded and/orcordless VoIP phone 110, any VoIP adapter 112 (e.g., an analog telephoneadapter (ATA)), and any VoIP enabled personal computer (PC) 114. Whilefour example VoIP-enabled devices 108, 110, 112 and 114 are illustratedin FIG. 1, the example communication system 100 may include any numberand/or type(s) of VoIP devices.

The example VoIP-enabled devices 108, 110, 112 and 114 of theillustrated example are configured to establish one or morecommunication sessions using, for example, Internet protocol (IP) basedcommunication, universal datagram protocol (UDP) based communication,transmission control protocol (TCP) based communication, TCP/IP basedcommunication, file transfer protocol (FTP) communication, and/orhyper-text markup language (HTML) based communication. Example data thatmay be exchanged and/or transmitted via a communication sessionincludes, but is not limited to, digital pictures, audio, video, datafiles, advertisements, coupons, website information, etc. Communicationsessions may also be used to send and/or exchange any number and/ortype(s) of participant information (e.g., a conference call participantidentification number, a password, a personal identification number(PIN), a user name, and/or a phone number).

Conference call communication sessions may be initiated and/orestablished during and/or after the establishment of a VoIPcommunication session, and as directed and/or initiated by a user of aVoIP-enabled device (e.g., the VoIP phone 110). For example, aparticipant may join a conference call from the VoIP-enabled devices108, 110, 112 and 114 by pressing one or more general purpose and/ordedicated keys and/or buttons of an input interface, such as a keyboard,keypad, and/or touch screen, and/or by dialing the call-in telephonenumber and entering an authorization code. The VoIP-enabled device thenresponds to the user input by establishing a connection to theconference call based on, for example, the call-in telephone numberand/or an IP address of the example conference call manager 102 storedin the memory of the VoIP-enabled device or as entered by theparticipant. The example conference call manager 102 of FIG. 1 may belocated at a company associated with one or more of the conference callparticipants, and/or may be located at a third party conference callservice provider, such as AT&T.

To provide IP-based communication services, the example system 100 ofFIG. 1 includes any type(s) of communication networks, three of whichare illustrated in FIG. 1 with reference numerals 116, 118 and 120. Theexample communication networks 116, 118, and 120 are implemented inaccordance with, for example, one or more past, current and/or futurestandard such as the 3^(rd) Generation Partnership Program (3GPP)Internet Multimedia Subsystem (IMS) standard(s) and/or specification(s).In the illustrated example, each of the networks 116, 118, and 120 isassociated with a different service provider; however, they could beassociated with one service provider and/or two or more of the networksmay be associated with the same service provider. While three networks116, 118, and 120 are illustrated in FIG. 1, the communication system100 of FIG. 1 may include any number and/or type(s) of communicationnetworks operated by any number of service providers.

To initiate, receive, establish, complete and/or route any type(s) ofcommunication sessions (e.g., VoIP telephone calls), the examplecommunication network 116 of FIG. 1 includes and/or communicates withany portion of any type(s) of VoIP call processor(s) (not shown) and/orVoIP gateway(s) 122. In the example of FIG. 1, the example communicationnetwork 116 includes an interface to and/or contains a portion of apublic switched telephone network (PSTN) 124, and an interface to and/orcontains a portion of a public land-mobile network (PLMN) 126 (e.g., acellular network). Additionally or alternatively, the example network116 may include an interface to and/or contain a portion of any type(s)of communication networks. For example, using any type(s) oftechnique(s), method(s), protocol(s) and/or technology(-ies), the VoIPgateway 122 and the PSTN 124 can facilitate telephone calls between aPSTN-based phone (not shown) and any of the example VoIP devices 108,110, 112, and 114. In the illustrated example of FIG. 1, the VoIPgateway(s) 122 implement a media gateway control function (MGCF). In theexample of FIG. 1, the gateway(s) 122 are implemented by and/or withinthe example communication network 116. However, the example gateway(s)122 may be associated with the communication network 116, the PLMN 126,the PSTN 124 and/or any other communication network.

The example PLMN 126 and/or the example PSTN 124 of FIG. 1 may beimplemented by any type(s) of communication device(s), switch(es),protocol(s), system(s) and/or technology(-ies). For instance, theexample PLMN 126 may include one or more cellular base stations that cantransmit cellular signals to and/or receive cellular signals from acellular communication device using any type(s) of protocols (e.g.,time-divisional multiple access (TDMA), code-divisional multiple access(CDMA), etc.).

In the illustrated example of FIG. 1, the example VoIP devices 108, 110,112, and 114 are communicatively coupled to the example communicationnetworks 116, 118, and 120 via any type(s) of public and/or private IPnetwork 106, such as the Internet. However, any type(s) of currentand/or future communication network(s), communication system(s),communication device(s), transmission medium(s), protocol(s),technique(s) and/or standard(s) could be used to communicatively couplethe VoIP devices 108, 110, 112, and 114 to one or more of thecommunication networks 116, 118, and 120. The example VoIP devices 108,110, 112, and 114 may be coupled to the IP Network 106 via any type(s)of current and/or future device(s), technology(-ies) and/or method(s),including voice-band modem(s), digital subscriber line (DSL) modem(s),cable modem(s), Ethernet transceiver(s), optical transceiver(s), virtualprivate network (VPN) connection(s), Institute of Electrical andElectronics Engineers (IEEE) 802.11x (a.k.a. WiFi) transceiver(s), IEEE802.16 (a.k.a. WiMax), access point(s), access provider network(s), etc.Moreover, the example IP Network 106 may extend geographically toinclude a location near to and/or encompassing one or more VoIP devices108, 110, 112, and 114. For example, the IP Network 106 and/or a publicand/or private access provider network (e.g., an example access providernetwork 128) may include a wireless access point (not shown) by which,for example, the example WiFi IP phone 108 connects to the IP Network106. In some examples, an access provider network includes a DSL accessmultiplexer (DSLAM) that facilitates communicative coupling between asubscriber having a DSL modem and the IP Network 106. In some examples,an access provider network includes a cable modem headend thatfacilitates communicative coupling between a subscriber having a cablemodem and the IP Network 106. In general, an access provider network 128provides, implements and/or facilitates a communicative coupling betweena VoIP device 108, 110, 112, and 114 and the IP network 106.

The example VoIP devices 108, 110, 112, and 114 of FIG. 1 may becommunicatively coupled to an access provider (e.g., the example accessprovider network 128) and/or the IP network 106 via any type(s) ofpublic and/or private local area networks (LANs) located within, forexample, a residence, school and/or place of business, and/or via anytype(s) of router(s), bridge(s) and/or gateway(s) located within and/orcoupled to such public and/or private locations and/or LANs. Forexample, the example VoIP telephone adapter 112 is communicativelycoupled to a PC 130 via a LAN 132. As described in further detail below,in the example of FIG. 1, the PC 130 or the PC 114 are used tofacilitate (e.g., via the web-based user interface 400 of FIG. 4) aninteraction between a participant and the conference bridge 104 and/orthe conference call manager 104 to manage a conference call and/or oneor more aspects thereof. Additionally, the PC 130 may be used to controland/or configure the example VoIP telephone adapter 112, the VoIP phone110, or any other communicatively coupled VoIP-enabled device.

While an example VoIP communication system 100 has been illustrated inFIG. 1, the communication networks 116, 118, and 120, the accessprovider network 128, devices, servers, systems, gateways, portals,and/or processors illustrated in FIG. 1 may be combined, re-arranged,divided, eliminated and/or implemented in any of a variety of ways. Forexample, the example conference call manager 102 and/or the componentsor devices thereof may be implemented by and/or within a common serveror on distributed servers. Further, the example VoIP devices 108, 110,112, and 114, the example conference call manager 102, and/or, moregenerally, the example communication networks 116, 118, and 120 may beimplemented by hardware, software, firmware and/or any combinationthereof. Moreover, the example communication system 100 may includeadditional devices (e.g., servers, systems, gateways, portals, and/orprocessors) than those illustrated in FIG. 1 and/or may include morethan one of any or all of the illustrated communication networks, accessprovider networks, devices, systems, and/or gateways.

FIG. 2 illustrates an example manner of implementing the exampleconference call manager 102 of FIG. 1. Generally, the example conferencecall manager 102 stores and implements the policies that dictate thesettings, restrictions, and/or rules of a conference call. For example,the conference call manager 102 is configured to receive volumeadjustment requests and, in conjunction with the conference bridge 104,processes the requests to convey customizable audio signals to thedifferent communication devices of the participants. Further, theexample conference call manager 102 prevents interruptions of highlyranked participants (e.g., a supervisor or conference call moderator) bylower ranked participants (e.g., an associate or newly hired employee)according to a hierarchy tracked and stored by, for example, theconference call manager 102.

To perform, inter alia, the above tasks, the example conference callmanager 102 includes a participant recorder 202, a current speakeridentifier 204, an interrupt handler 206, an adjustment requesteridentifier 208, an inflection detector 210, a queue 212, a queue manager214, preference settings 216, and, as described above in connection withFIG. 1, a conference bridge 104, all of which are communicativelycoupled and implemented by and/or within, for example, common ordistributed media servers of a conference call service provider (e.g.,AT&T). Further, the example components of the example conference callmanager 102 and, more generally, the example communication system 100 ofFIG. 1, including the conference bridge 104, the participant recorder202, the current speaker identifier 204, the interrupt handler 206, theadjustment requester identifier 208, the inflection detector 210, thequeue 212, the queue manager 214, and/or the preference settings 216 maybe implemented by hardware, software, firmware and/or any combination ofhardware, software, and/or firmware.

As described above, a communication session between a participant andthe conference call manager 102 is initiated by, for example, theparticipant dialing a common telephone number assigned to the conferencecall manager 102. The participant recorder 202 stores identifyinginformation for some or all of the participants that access theconference call using any of type(s) of data structure(s), array(s),table(s), database(s) or variable(s). Example identifying informationincludes, by way of example, not limitation, a conference callparticipant identification number, a password, a personal identificationnumber (PIN), a user name, and/or a phone number. The participantrecorder 202 of the illustrated example associates the identifyinginformation it receives from callers with the communication device(s)used to communicate information to the conference call manager 102.Additionally or alternatively, the VoIP-enabled device of eachparticipant may include a device identifier that uniquely identifies theVoIP-enabled device, such as a manufacturing serial number, a mediaaccess control (MAC) address, etc. The example participant recorder 202of the illustrated example stores phone numbers as identifiers for theparticipants. In some examples, where a participant joins the conferencecall using the PC 114 or the VoIP telephone adapter coupled to the PC130 of FIG. 1, additional or alternative identifiers (e.g., IPaddresses) may be utilized by the participant recorder 202.

As illustrated in FIG. 2, the participant recorder 202 is incommunication with the preference settings 216. In the illustratedexample, the preference settings 216 are files stored in memory (e.g., adatabase stored in memory of the conference bridge 104) accessible bythe participant recorder 202. Some or all of the settings mayalternatively or additionally be created anew at the start or creationof the conference call. Such newly created settings are added to theentries in the memory by the participant recorder 202. For example, fora system in which the conference call manager 102 typically managesrepeat participants, the preference settings 216 of the participants maybe semi-permanently stored in memory. Additionally or alternatively,where new participants typically comprise, for example, a majority ofthe participants, the preference settings 216 may be temporarily storedwith the entries created by the participant recorder 202 during, forexample, the duration of the conference call (e.g., until noparticipants are connected to the conference call manager 102 and/or theconference bridge 104). The entries may then be purged.

In the example of FIG. 2, the preference settings 216 include or arelinked to a plurality of priority rankings for the participants basedon, for example, a corporate position (chief executive officer (CEO),secretary, chief patent counsel, etc.). As described in greater detailbelow, the priority rankings are used to, for example, settle attemptsof multiple participants to speak substantially simultaneously. Thepreference settings 216 of FIG. 2 further include a plurality ofamplification settings associated with corresponding participants of theconference call. As described in greater detail below, a firstparticipant (participant A) may consider the audio signal from thecurrent speaker (participant B) to be too loud. However, participant Amay consider the audio signals from the remainder of the participants tobe received at an acceptable volume level. Using the example theweb-based user interface 400 of FIG. 4, participant A may engage acurrent speaker soft-key 412 on a webpage associated with or incommunication with the conference call manager 102 to indicate a desireto lower (or raise) the amplification setting (e.g., by a factor rangingfrom 1-100) associated with the current speaker. The “current speaker”is automatically identified by the current speaker identifier 204. Theadjustment requester identifier 208 automatically identifies theparticipant (e.g., participant A) that requested an adjustment of theamplification setting associated with the current speaker. Theparticipant recorder 202 responds to the user input and theidentifications made by the current speaker identifier 204 and theadjustment requester identifier 208 by making an entry in a preferencefile in the preferences settings 216 corresponding to the userrequesting the amplification change. Alternatively, a participant mayfeel that the overall volume of the conference call is too loud or softand, thus, may engage a universal volume soft-key 418 on the webpage toindicate a desire to raise or lower the overall volume. In response, theparticipant recorder 202 adjusts a universal amplification setting in apreference file in the preference settings 216 corresponding to the userrequesting the universal volume setting change.

The conference bridge 104 references the preference settings 216 andsets the amplification level(s) based thereon before conveying the audiosignals to the communication devices of each participant. In the exampleof FIG. 2, one or more mixers and/or buffers of the conference bridge104 are configured to utilize the amplification settings to calculate anaggregate audio signal (e.g., the sum of the inputs being received fromunblocked participants) to be conveyed to each participant. Inparticular, each received audio signal received from each participantadjusted (e.g., as part of a matrix multiplication operation) using thecorresponding amplification setting retrieved from the intendedparticipant's preference file before the audio signal is added to theaggregate audio signal. The amplification and/or preference settings 216may be used in other example operations to provide a communicationdevice a customized audio signal representing the preference(s) of auser of that communication device. The preference settings 216 may bealtered at any time during the call via, for example, a web-based userinterface (e.g., the example user interface 400 of FIG. 4).

To compensate for any loss of expression caused by the volumeadjustment(s) described above, the example conference call manager 102of FIG. 2 includes an inflection detector 210. The example inflectiondetector 210 of FIG. 2 monitors the conference call (e.g., via acommunication interface, buffer(s), and/or mixer(s) of the conferencebridge 104) for any sharp or dramatic change(s) in volume (e.g., as aresult of yelling) from any of the participants. Such a change in volumemay be lost in the transmission of the audio signal to the communicationdevices of certain participants due to, for example, a low amplificationsetting associated with a current speaker. The example inflectiondetector 210 is configured to visually communicate this type ofexpression. In particular, the example inflection detector 210 monitorsincoming audio signals before and/or during the calculation of theoutgoing aggregate audio signals described above. In response to adetected sharp variation in volume, the inflection detector 210 sends aninstruction, (e.g., via the IP network 106) to a server maintaining awebpage associated with the conference call to cause the webpage todisplay an indicator (e.g., the indicator 416 of FIG. 4) and/orcorresponding text (e.g., ‘Yelling’ or ‘Loudly’). Thus, while listeningparticipants may not audibly receive the intended expression of thecurrent speaker (e.g., due to volume adjustments made according to thepreference settings 216), the inflection detector 210 visually informsparticipants of any pre-adjustment variations in, for example, the toneof the current speaker.

To organize the conference call and prevent unwarranted interruptions,the example interrupt handler 206 of FIG. 2 includes the queue 212 andthe queue manager 214. Generally, the example interrupt handler 206monitors the conference call for simultaneous incoming audio signals,blocks the audio signals of lower ranked participants (e.g., preventsthe transmission to other participants by removing the incoming audiosignal of the lower ranked participant from the outgoing aggregate audiosignal to be conveyed to participants), and places an identifiercorresponding to the blocked participant in the queue 212. The order ofidentifiers in the queue 212 determines the order in which the audiosignals of the blocked participants will be unblocked. To determinewhether one participant should be blocked from interrupting anotherparticipant, the interrupt handler 206 obtains and/or referencesidentifying information stored by the participant recorder 202, which,as described above, has access to the preference settings 216 and, thus,the priority rankings of the participants. The interrupt handler 206then performs a comparison of the priority rankings associated with thecompeting speakers. The results of the comparison are used to enforce adesired policy. In the illustrated example, a higher ranked participantis able to cut off (e.g., cause a blockage of the audio signal of) acurrently speaking lower ranked participant. In other words, theincoming audio signal of the current speaker may be blocked by anincoming audio signal from a higher ranked speaker such as, for example,a moderator that is assigned the highest priority ranking. Similarly,when two speakers attempt to speak at substantially the same time, thevoice of the higher ranking speaker will be passed, while the voice ofthe lower ranking speaker will be blocked. When participants are of thesame priority ranking, no blocking of any audio signal may occur and amixed (e g, summed) audio signal of each similarly ranked participantmay be conveyed.

In the illustrated example, the queue manager 214 manages and/ororganizes the queue 212 according to a behavior-based policy.Specifically, the order in which blocked participants are allowed tospeak (e.g., by unblocking the corresponding audio signal) is based on,for example, a point system. In the illustrated example, the queuemanager 214 places the participant having the highest point total at thefront of the queue 212, thereby allowing that participant to speak firstamong the members of the queue 212. Rules of the behavior-based policyare implemented to, for example, reward patient participants and/or tocurb any adverse effects caused by aggressive participants (e.g.,frequent interruptions). The queue manager 214 assigns some or all ofthe participants an initial point value, which is stored in, forexample, the preference settings 216, memory linked to the queue 212,and/or any other suitable location. The point value corresponding toeach participant may be retained for future conference calls, purged atthe conclusion of the conference call, or maintained otherwise by thequeue manager 214. The queue manager 214 has access to the point valueand manipulates the point value to reflect the desirable queue position(e.g., according to the behavior-based policy as determined by, forexample, a conference call moderator) of the corresponding participant.Example point allocations include lowering the correspondingindividual's point total for each attempted interruption, lowering thecorresponding individual's point total for extended periods of speaking(e.g., when a participant “has the floor” for a time greater than apredetermined threshold), assigning an initial point value based on apriority ranking or how many participants are currently in the queue212, raising the corresponding individual's point total for highlyrelevant statements or questions, lowering the correspondingindividual's point total for substantially irrelevant statements orquestions, and/or adjusting the corresponding individual's point totalin response to input received from other participants (e.g., feedbackprovided via the web-based user interface 400 of FIG. 4). For example,one participant may inform the conference call manager 102 that thecurrently speaking participant has uttered a highly relevant orirrelevant statement or phrase. In the illustrated example, therelevancy of a statement or question is automatically determined basedon a comparison between spoken words or phrases (e.g., as detected via aspeech recognition module implemented by the example processor 501) andone or more keywords associated with the conference call (e.g., in anagenda stored in memory linked to the conference call manager 102). Inthe illustrated example, more points are awarded to those participantsthat say certain words more often. The keywords may be chosen by amoderator, taking from a title of the conference call, or otherwiseselected. Additionally or alternatively, the conference participants canuse the web-based user interface 400 to enter feedback on the relevancyof questions and/or statements made by a speaker. Such feedback can becompiled by the queue manager 214 and used to increment or decrement thepoint total of the corresponding speaker.

Alternatively, the queue manager 214 may manage and/or organize thequeue 212 such that the first (in time) participant to unsuccessfullyattempt to interrupt a higher ranked participant is placed at the frontof the queue 212 and is, thus, unblocked first. Alternatively, the queuemanager 214 may sort the identifiers in the queue 212 such that thehighest ranked blocked participant is placed at the front of the queue212 and is, therefore, unblocked first.

The current speaker identifier 204 may utilize, for example, voiceverification and/or speaker recognition systems to associate theincoming audio signal(s) with current speaker(s). The voice verificationand/or speaker recognition system(s) may be implemented by softwareexecuted on a processor (e.g., the processor 510 of the processorplatform 500 of FIG. 5). Additionally or alternatively, the currentspeaker identifier 204 may use any available identifying information(e.g., a conference call participant identification number, a password,a personal identification number (PIN), a user name, and/or a phonenumber) transferred to the conference call manager 102 to identifyspeaker(s) by, for example, detecting the source (e.g., computeraddress) of an incoming audio signal. For example, if the examplecurrent speaker identifier 204 illustrated in FIG. 2 obtains aconference call participant identification number from a communicationdevice transmitting incoming audio data, the identification number isthen used to determine an identity of the current speaker by referencingthe participant's record, which correlates identification number(s) toparticipant(s) of the conference call. The example current speakeridentifier 204 of the illustrated example ignores (e.g., excludes in theprocess of identifying the current speaker) incoming audio signals beingtransmitted below a predetermined threshold level (e.g., a decibellevel), thereby excluding ambient noise not associated with the currentspeaker.

Similarly, the adjustment requester identifier 208 may utilizeidentifying information sent by one or more communication devices to theconference call manager 102 to determine the identity of an adjustmentrequester. In the illustrated example of FIG. 2, when a participantrequests an adjustment of an amplification setting associated with thecurrent speaker or a universal volume setting via the web-based userinterface 400 of FIG. 4, the adjustment requester identifier 208determines the IP address of the communication device that engaged avolume adjustment key on the web-based user interface 400. Theadjustment requester identifier 208 can then reference the files managedby the participant recorder 202 to determine which participant isassociated with the detected IP address.

While an example manner of implementing the conference call manager 102of FIG. 1 has been illustrated in FIG. 2, one or more of the elements,processes and/or devices illustrated in FIG. 2 may be combined, divided,re-arranged, omitted, eliminated and/or implemented in any other way.Further, the example conference bridge 104, the example participantrecorder 202, the example current speaker identifier 204, the exampleinterrupt handler 206, the example adjustment requester identifier 208,the example inflection detector 210, the example queue 212, the examplequeue manager 214, the example preference settings 216, and/or, moregenerally, the example conference call manager 102 of FIG. 2 may beimplemented by hardware, software, firmware and/or any combination ofhardware, software and/or firmware. Thus, for example, any of theexample conference bridge 104, the example participant recorder 202, theexample current speaker identifier 204, the example interrupt handler206, the example adjustment requester identifier 208, the exampleinflection detector 210, the example queue 212, the example queuemanager 214, the example preference settings 216 and/or, more generally,the example conference call manager 102 could be implemented by one ormore circuit(s), programmable processsor(s), application specificintegrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)),and/or field programmable logic device(s) (FPLD(s)), etc. When any ofthe appended claims are read to cover a purely software implementation,at least one of the example conference bridge 104, the exampleparticipant recorder 202, the example current speaker identifier 204,the example interrupt handler 206, the example adjustment requesteridentifier 208, the example inflection detector 210, the example queue212, the example queue manager 214, the example preference settings 216and/or, more generally, the example conference call manager 102 arehereby expressly defined to include a tangible medium such as a memory,DVD, CD, etc. Further still, the example conference call manager of FIG.2 may include one or more elements, processes and/or devices in additionto, or instead of, those illustrated in FIG. 2, and/or may include morethan one of any or all of the illustrated elements, processes anddevices.

FIGS. 3A, 3B, and 3C illustrate a flowchart representing machinereadable instructions that may be executed to implement the system ofFIGS. 1-2. The example machine accessible instructions of FIGS. 3A, 3B,and/or 3C may be executed by a processor, a controller and/or any othersuitable processing device. For example, the example machine accessibleinstructions of FIGS. 3A, 3B, and/or 3C may be embodied in codedinstructions stored on a tangible medium such as a flash memory, or RAMassociated with a processor (e.g., the example processor 501 discussedbelow in connection with FIG. 5). Alternatively, some or all of theexample flowcharts of FIGS. 3A, 3B, and/or 3C may be implemented usingany type(s) of ASIC(s), PLD(s), FPLD(s), discrete logic, hardware,firmware, etc. Also, some or all of the example flowcharts of FIGS. 3A,3B, and/or 3C may be implemented manually or as any combination(s) ofthe foregoing techniques, for example, as any combination of firmware,software, discrete logic and/or hardware. Further, although the examplemachine accessible instructions of FIGS. 3A, 3B, and 3C are describedwith reference to the flowcharts of FIGS. 3A, 3B, and 3C, many othermethods of implementing the conference call manager 102 and/or, moregenerally, the VoIP communication system 100 of FIGS. 1-2, including theconference bridge 104, the participant recorder 202, the current speakeridentifier 204, the interrupt handler 206, the adjustment requesteridentifier 208, the inflection detector 210, the queue 212, the queuemanager 214, and/or the preference settings 216 may be employed.Further, the order of execution of the blocks of FIGS. 3A, 3B, and/or 3Bmay be changed, and/or some of the blocks described may be changed,eliminated, sub-divided, or combined. Additionally, the example machineaccessible instructions of FIGS. 3A, 3B, and/or 3C may be carried outsequentially and/or carried out in parallel by, for example, separateprocessing threads, processors, devices, discrete logic, circuits, etc.

FIGS. 3A, 3B, and 3C are described below in conjunction with an exampleuser interface 400 illustrated in FIG. 4 to be used by a participant ofa conference call. The example user interface 400 is implemented on awebsite hosted by a server that is communicatively coupled (e.g., viathe IP Network 106 of FIG. 1) to the conference call manager 102 ofFIG. 1. As described in further detail below, the website enables theparticipant to configure, control and/or monitor a VoIP-enabled deviceand/or one or more aspects of the conference call (e.g., volumesettings, queue position, interruption warning, etc.). Further, one ormore webpages associated with the website and served by the server maybe personalized to individual participant(s) of the conference callbased on, for example, participant or device identification information,account information, etc. associated with each individual participant orgroup of participants.

The website may be accessed via, for example, a web browser executed ona personal computer, a cellular phone, a personal digital assistant(PDA), or any other device capable of accessing a website. In someexamples, the website is accessed by a web browser on a VoIP-enabled PCon which the participant is making the call to the conference calldevice.

The machine readable instructions of FIG. 3A begin when one or morecommunication device(s) (e.g., the VoIP-enabled devices 108, 110, 112,and/or 114 of FIG. 1) attempt to join a conference call by, for example,dialing a common telephone number or IP address assigned to theconference call manager 102 of FIG. 1, which is configured to implementa conference call and/or the policies thereof (block 302). Participantsthat successfully join the conference call (e.g., by entered the correctauthorization code) are enrolled (e.g., granted access to the conferencecall) and an identifier associated with each enrolled participants isdetected and stored in the participant record 202 of FIG. 2 to track theparticipants during and/or after the conference call (block 304). Forexample, at the onset of the conference call, participants may berequired to enter a password, key, registration number, and/or any othertype of identifying information before being enrolled. Additionally oralternatively, as described above, identifying information may beautomatically transmitted to the conference call manager 102 in, forexample, data packets sent over an IP network (e.g., the IP Network 106of FIG. 1). For example, a communication device may automaticallytransmit a device identification number that is associated with a knownparticipant. In some examples, the telephone number or IP address fromwhich the participant called may be used as identifying information.

The identifying information received by the conference call manager 102may include or may be linked to a database including a title (e.g., vicepresident, manager, associate), an assignment (e.g., marketing, sales,distribution), a position (e.g., lower level, mid-level, very importantperson), or any other identifier that may be used to establish ahierarchy of participants (block 306). The hierarchy may be setaccording to the policies of the conference call, which may bedetermined by, for example, a moderator or a host of the conference calland stored in memory of the conference call device. In the illustratedexample of FIG. 3A, the hierarchy is displayed to indicate the identityof the participants of the conference call (block 308). An examplehierarchy 402 is illustrated in the example user interface 400 of FIG.4. The example hierarchy 402 includes names and ranks/titles arranged ina list format, which may be sorted, scrolled, and/or rearranged usingany type(s) of techniques or methods.

Upon the detection of an incoming audio signal (block 310), the currentspeaker identifier 204 determines the identity of the source of theaudio signal (i.e., the current speaker) (block 312). For example, acommunication interface of the conference bridge 104 of FIG. 1 receivesan input from a communication device (e.g., the PC 114 of FIG. 1) andpasses it to the current speaker identifier 204 of FIG. 2. The currentspeaker identifier 204 determines the source of the input (e.g., viaspeaker recognition or identifying information transmitted from thecommunication device). The current speaker identifier 204 stores (e.g.,temporarily in a register of memory) the identity of the current speakerand/or cooperates with the participant recorder 202 of FIG. 2 todesignate an entry corresponding to a participant in a database as thecurrent speaker.

At any given time, one or more participants may attempt to interject orinterrupt the current speaker and/or two speakers may attempt to speakat the same time. Such an attempt is manifested by two audio signalsbeing simultaneously transmitted to the conference bridge 104 at avolume level audible to the other participants (block 314). FIG. 3Billustrates a flowchart representation of machine-readable instructionsthat may be executed in response to such a detection (block 316). Whentwo audio signals are detected, the current speaker identifier 204identifies the two speakers (block 318). If one of the speakers wasspeaking at the time another speaker spoke, the second speaker is aninterrupter and is referred to as the second speaker in the following.If neither of the speakers is an interrupter (the speakers areattempting to speak at substantially the same time), the first detectedspeaker is designated the “current speaker” and the second detectedspeaker is designated the “second speaker” in the following methodology.Alternatively, the designation of “current speaker” and “second speaker”can be arbitrary when, for example, it is difficult to determine whichspeaker spoke first. Using the identifying information of the speakers,the interrupt handler 206 compares a priority ranking of the secondspeaker (e.g., as obtained from the participant record 202 of FIG. 2) tothe priority ranking of the current speaker (as identified above atblock 312) (block 320). In the illustrated example of FIG. 3B, if thepriority ranking of the second speaker is greater than the priorityranking of the current speaker, the interrupt handler 206 blocks theaudio of the current speaker is blocked, thereby enabling the higherranked second speaker to be heard (block 322). For example, the audio ofthe current speaker may be blocked by restricting one or more devices(e.g., mixer(s) and/or buffer(s) of the conference bridge 104 of FIG. 1)from adding the audio signal originating from the communication deviceof the current speaker to the aggregate conference call output stream.

Further, the interrupt handler 206 sends the identifier associated withthe blocked participant to the queue 212 of FIG. 2 (block 324). In theillustrated example of FIG. 3B, the queue manager 214 places theidentifier of the blocked speaker in the queue 212 at a positiondictated by a behavior-based policy. As described above, the queuemanager 214 implements a point system to determine the order in whichblocked participants are subsequently allowed to speak after beingplaced in the queue 212. Implementing the point system includesassigning an initial point total to some or all of the participants andstoring the point total(s) in the preference settings, in memory linkedto the queue 212, and/or at any other suitable location. In theillustrated example, the queue manager 214 references the point total(s)when organizing the queue 212 and adjusts the point total(s) accordingto the behavior-based policy described herein. The behavior-based policyof the illustrated example dictates that the participant having thehighest point total in the queue 212 is allowed to speak first. Thequeue manager 214 may alternatively organize the queue 212 in any otherway (e.g., first-in-first-out (FIFO), last-in-first-out (LIFO), bypriority ranking, etc.). Upon an addition to (or removal from) the queue212, the queue manager 214 organizes the queue 212 (e.g., reorders theidentifiers of blocked participant according to their correspondingpoint totals) to reflect the order or status of the currently blockedparticipants (block 326).

Returning to block 320, if the priority ranking of the second speaker isless than or equal to that of the current speaker, the audio of thesecond speaker is blocked (block 328) and the corresponding identifieris conveyed to the queue (block 330). Upon such an attemptedinterruption, the interrupt handler 206 causes an interruption indicatorto be conveyed to the lower ranked participant (block 332). For example,as illustrated in the example user interface 400 of FIG. 4, a warningsymbol 404 is displayed (e.g., as a flashing image) in a section 406dedicated to informing the participant of a blocked attempt to interruptanother participant. Moreover, the blocked participant may be informed,via an indicator 408 in a section 410 dedicated to the queue 212, of aqueue position (e.g., how many other participants in the queue 212 willbe unblocked before the blocked participant is allowed to speak). In theillustrated example, the queue manager 214 decrements the secondspeaker's point total according to the behavior-based policy to reflecta tendency of the second speaker to interrupt other participants (block334). Again, in response to addition(s) to (or removal(s) from) thequeue 212, the queue manager 214 organizes the queue 212 (block 326),after which control returns to the machine-readable instructions of FIG.3A (block 336).

As described above, a participant may consider the volume of the currentspeaker to be too loud or soft and, in response, may request a volumeadjustment of the current speaker as transmitted to the communicationdevice of the requesting participant (FIG. 3A, block 338). In theillustrated example user interface 400 of FIG. 4, the request is made byselecting soft-key(s) (e.g., images of button(s)), such as currentspeaker soft-key(s) 412 or universal volume setting soft-key(s) 418,disposed on the HTML page associated with the conference call. FIG. 3Cis a flowchart representative of example machine-readable instructionsthat may be executed in response to such a request (block 340).

Upon detecting a request, the adjustment requester identifier 208identifies the participant that requested the adjustment (block 342) by,for example, determining an IP address from which the request was made.Specifically, clicking (e.g., using a mouse or keyboard key of the PC114 of FIG. 1) one of the dedicated keys 412 or 418 causes the webbrowser to send a message (e.g., a series of data packets) over anetwork (e.g., the IP Network 106 of FIG. 1) to the conference callmanager 102 of FIGS. 1 and/or 2. The transmitted message includes the IPaddress of the sender along with the payload of the transmitted message.Other types of identifying information (e.g., a device identifierassociated with the communication device accessing the website) may betransmitted (e.g., as a portion or object of the message) and used bythe adjustment requester identifier 208 of the conference call manager102 to obtain the identity of the requesting participant.

When the source of the request has been obtained, the adjustmentrequester identifier 208 of FIG. 2 then determines which participant isassociated with the source. For example, the obtained IP address may belinked to one of the participants in a database maintained by theparticipant recorder 202 of FIG. 2 as a semi-permanent or temporaryentry. The IP address, or other identifying information, may have beenlinked to a participant by the participant recorder 202 when theparticipant joined the conference call. For example, the participant maybe required to enter a username or other identification information whenaccessing (e.g., logging onto) the website. The IP address and theentered identification information may be logged by the participantrecorder 202 of FIG. 2 and/or stored for (at least) the duration of theconference call.

Using the identity information obtained by the adjustment requesteridentifier 208, the participant recorder 202 adjusts the preferencesettings of the adjustment requester in accordance with the informationin the request message. The payload of the transmitted messages includesthe type(s) of adjustment requested, the magnitude of the requestedadjustment, and/or the direction of the requested adjustment (e.g.,louder or softer). The type of requested adjustment may be a request toadjust the universal volume setting of the conference call astransmitted to the communication device of the requesting participant.For example, the requesting participant may feel that the overall volumeof the conference call is too loud or soft and may not be able tofurther adjust the volume settings of the communication device receivingthe conference call audio signal. In the illustrated example of FIG. 4,the universal volume key(s) 418 may be engaged to make such anadjustment. If the type of the request is a universal adjustment (block344), the participant recorder 202 adjusts a universal amplificationsetting in the preference settings associated with the requestingparticipant (block 346). The conference bridge 104 then references thepreference settings 216 when conveying the audio signal to theadjustment requester (block 348), and the altered universalamplification setting causes the aggregate audio signal (e.g., thecombination of unblocked audio signals being received from theconference call participants) being conveyed to the adjustment requesterto be raised or lowered in volume without affecting the audio signal(s)being conveyed to other participants.

Alternatively, the payload of the transmitted message may indicate thatone of the current speaker keys 412 was engaged. If so, theamplification setting associated with the current speaker (as identifiedabove at block 312) in the preference settings of the adjustmentrequester is raised or lowered by the participant recorder 202 (block350). Thus, although the requesting participant may not be aware of theidentity of the current speaker, the volume at which the current speakeris received by the requesting participant is altered for the duration ofthe call and, if the records from the call are maintained and reused insubsequent call(s), the volume settings are applied in those calls. Theconference bridge 104 then conveys the audio signal to the requestingparticipant according to the newly altered preference settings 216,without affecting the audio signals conveyed to the other participants(block 348). For example, as described above, the conference bridge 104of the conference call manager 102 may multiply (e.g., via any of avariety of matrix operations) an incoming audio signal of the currentspeaker by an amplification setting (e.g., a percentage factor)associated with the current speaker in the preference file of theadjustment requester, such that the incoming audio signal of the currentspeaker forms a customized portion of the aggregate outgoing audiosignal to be conveyed to the adjustment requester. Control then returnsto the machine-readable instructions of FIG. 3A (block 352).

As described above, the inflection detector 210 of FIG. 2 monitors theconference call (e.g., via a communication interface, buffer(s), and/ormixer(s) of the conference bridge 104) for any sharp or dramaticchange(s) in volume (e.g., as a result of yelling) from any of theparticipants. If such an inflection is detected (block 354), theinflection detector 210 sends a message or instruction (e.g., via the IPnetwork 106) to a server maintaining the example user interface 400thereby, causing the user interface 400 to visually communicate a typeof expression to some (e.g., participants that have requested a volumeadjustment of the current speaker) or all of the participants in thededicated voice inflection section 414 of FIG. 4 (block 356). Forexample, the indicator 416 of FIG. 4 may include text or one or moreimages conveying that the current speaker is yelling or screaming. Thus,while some listening participants may not audibly receive the intendedexpression of the current speaker (e.g., due to volume adjustments madeaccording to the preference settings 216), the inflection detector 210visually informs participants of any inflections in, for example, thetone of the current speaker.

To further implement the behavior-based policy, the queue manager 214automatically determines the relevancy of the statements and/orquestions being made by the current speaker. In response to such adetermination, the queue manager 214 adjusts the point total associatedwith the current speaker according to the behavior-based policy.Specifically, the queue manager 214 compares (e.g., via a speechrecognition module implemented by the example processor 501) thecontents of the current speaker's speech to one or more keywordsassociated with the conference call (e.g., in an agenda set by amoderator and stored in memory linked to the queue manager 114) (block358). If one or more statements are determined to be substantiallyrelevant (e.g., the current speaker used keyword(s) frequently in apredetermined time period) or substantially irrelevant (e.g., thecurrent speaker used keyword(s) infrequently, if any, of keywords weredetected over a predetermined period of time), the point totalassociated with the current speaker is adjusted accordingly (block 360).In particular, the queue manager 214 increments the point totalassociated with the current speaker in response to detecting asubstantially relevant statement or question, and the queue manager 214decrements the point total associated with the current speaker inresponse to detecting a substantially irrelevant statement or question.

Further, the queue manager 214 can receive feedback from listeningparticipants (e.g., participants other than the current speaker)regarding the relevancy of the statements being made or the questionsbeing asked by the current speaker. In the illustrated example,participants input feedback via the web-based user interface 400 of FIG.4, which conveys received feedback to the queue manager 214 (e.g., viathe IP network 106). In particular, the example user interface 400 ofFIG. 4 includes soft-key(s) (e.g., images of button(s)), such asrelevancy key(s) 420, disposed on the HTML page associated with theconference call. If a participant feels that the current speaker ison-point (e.g., by asking relevant, productive, or useful questions),the participant may engage a high relevancy key 422. If a participantfeels that the current speaker is off-point (e.g., wasting time byasking irrelevant questions), the participant may engage a low relevancykey 424. In the illustrated example of FIG. 3A, such an engagement ofthe relevancy key(s) 420 is referring to as a vote. In other words, theengaging participant is voting to reduce the point total associated withthe current speaker that determines queue positioning. If a vote isreceived (block 362), the queue manager 214 adjusts the point totalassociated with the current speaker (block 364). In alternativeexamples, a predetermined threshold amount of votes must be receivedbefore the queue manager 214 adjusts the point total associated with thecurrent speaker. Preferably, the voting is anonymous to enableparticipants to frankly rate the relevancy of the current speakerwithout fear of reprisals.

The processes described above continue until the current speaker is donespeaking (block 366). When the current speaker is done speaking, asindicated, for example, by the absence of incoming audio for apredetermined duration of time (e.g., one second) the queue manager 214determines whether a duration that the current speaker held the floor(e.g., continuously spoke) exceeds a predetermined threshold (block368). The predetermined threshold is set (e.g., by a moderator) suchthat exceeding the threshold indicates that the current speaker held thefloor for a relatively long period of time compared to an averageduration of speaking. Thus, in response to the current speaker exceedingthe predetermined threshold duration, the queue manager 214 decrementsthe point total associated with the current speaker according to thebehavior-based policy (block 370). In the illustrated example of FIG.3A, the duration is tracked by the queue manager 214. In alternativeexamples, the current speaker identifier 204, the participant recorder202, or any other suitable component of the example conference callmanager 102 of FIG. 2 may track the duration of the current speaker'sspeaking session.

Then, the interrupt handler 206 of FIG. 2 reviews the queue 212 forblocked participants (block 372). If the queue 212 includes anidentifier of a participant, then the participant next in the queue 212is unblocked and the interrupt handler 206 of FIG. 2 causes theindicator 408 of FIG. 4 to convey that information to the unblockedparticipant (block 374). In the illustrated example of FIG. 3A, theparticipant in the first position of the queue 212 (e.g., with highestpoint total according to the behavior-based policy) is unblocked andenabled to contribute to the conference call. Alternatively, the queuemanager 214 may manage and/or organize the queue 212 according to otherpolicies, such as FIFO, LIFO, by priority ranking, etc. Further, theindication 408 displayed to the unblocked participant(s) may be animage, text (e.g., “You have the floor”), or a combination thereof. Theprocesses described above in FIGS. 3A-C may continue until, for example,a moderator has ended the conference call or no participants remain.

FIG. 5 is a block diagram of an example processor platform 500 capableof executing the machine readable instructions represented by FIGS. 3A-Cto implement the apparatus and/or methods disclosed herein. Theprocessor platform 500 can be, for example, a server, a personalcomputer, a laptop, a PDA, or any other type of computing device.

The processor platform 500 of the instant example includes a processor510 such as a general purpose programmable processor. The processor 510includes a local memory 511, and executes coded instructions 513 presentin the local memory 511 and/or in another memory device. The processor510 may execute, among other things, the example process illustrated inFIGS. 3A-C. The processor 510 may be any type of processing unit, suchas a microprocessor from the Intel® Centrino® family of microprocessors,the Intel® Pentium® family of microprocessors, the Intel® Itanium®family of microprocessors, the Intel XScale® family of processors,and/or the Motorola® family of processors. Of course, other processorsfrom other families are also appropriate.

The processor 510 is in communication with a main memory including avolatile memory 512 and a non-volatile memory 514 via a bus 516. Thevolatile memory 512 may be implemented by Synchronous Dynamic RandomAccess Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUSDynamic Random Access Memory (RDRAM) and/or any other type of randomaccess memory device. The non-volatile memory 514 may be implemented byflash memory and/or any other desired type of memory device. Access tothe main memory 512, 514 is typically controlled by a memory controller(not shown).

The processor platform 500 also includes an interface circuit 518. Theinterface circuit 518 may be implemented by any type of interfacestandard, such as an Ethernet interface, a universal serial bus (USB),and/or a third generation input/output (3GIO) interface.

One or more input devices 520 are connected to the interface circuit518. The input device(s) 520 permit a user to enter data and commandsinto the processor 510. The input device(s) can be implemented by, forexample, a keyboard, a mouse, a touchscreen, a track-pad, a trackball,isopoint and/or a voice recognition system.

One or more output devices 522 are also connected to the interfacecircuit 518. The output devices 522 can be implemented, for example, bydisplay devices (e.g., a liquid crystal display, a cathode ray tubedisplay (CRT), a printer and/or speakers). The interface circuit 518may, thus, typically include a graphics driver card.

The interface circuit 518 also includes a communication device such as amodem or network interface card to facilitate exchange of data withexternal computers via a network (e.g., an Ethernet connection, adigital subscriber line (DSL), a telephone line, coaxial cable, acellular telephone system, etc.).

The processor platform 500 also includes one or more mass storagedevices 526 for storing software and data. Examples of such mass storagedevices 526 include floppy disk drives, hard drive disks, compact diskdrives and digital versatile disk (DVD) drives. The mass storage device526, for example, may implement the example databases described above.

At least some of the above described example methods and/or apparatusare implemented by one or more software and/or firmware programs runningon a computer processor. However, dedicated hardware implementationsincluding, but not limited to, application specific integrated circuits,programmable logic arrays and other hardware devices can likewise beconstructed to implement some or all of the example methods and/orapparatus described herein, either in whole or in part. Furthermore,alternative software implementations including, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the example methods and/or apparatus describedherein.

It should also be noted that the example software and/or firmwareimplementations described herein are optionally stored on a tangiblestorage medium, such as: a magnetic medium (e.g., a magnetic disk ortape); a magneto-optical or optical medium such as an optical disk; or asolid state medium such as a memory card or other package that housesone or more read-only (non-volatile) memories, random access memories,or other re-writable (volatile) memories; or a signal containingcomputer instructions. A digital file attached to e-mail or otherinformation archive or set of archives is considered a distributionmedium equivalent to a tangible storage medium. Accordingly, the examplesoftware and/or firmware described herein can be stored on a tangiblestorage medium or distribution medium such as those described above orsuccessor storage media.

To the extent the above specification describes example components andfunctions with reference to particular standards and protocols, it isunderstood that the scope of this patent is not limited to suchstandards and protocols. For instance, each of the standards forInternet and other packet switched network transmission (e.g.,Transmission Control Protocol (TCP)/Internet Protocol (IP), UserDatagram Protocol (UDP)/IP, HTML, HyperText Transfer Protocol (HTTP))represent examples of the current state of the art. Such standards areperiodically superseded by faster or more efficient equivalents havingthe same general functionality. Accordingly, replacement standards andprotocols having the same functions are equivalents which arecontemplated by this patent and are intended to be included within thescope of the accompanying claims.

This patent contemplates examples wherein a device is associated withone or more machine readable mediums containing instructions, orreceives and executes instructions from a propagated signal so that, forexample, when connected to a network environment, the device can send orreceive voice, video or data, and communicate over the network using theinstructions. Such a device can be implemented by any electronic devicethat provides voice, video and/or data communication, such as atelephone, a cordless telephone, a mobile phone, a cellular telephone, aPersonal Digital Assistant (PDA), a set-top box, a computer, and/or aserver.

Additionally, although this patent discloses example software orfirmware executed on hardware and/or stored in a memory, it should benoted that such software or firmware is merely illustrative and shouldnot be considered as limiting. For example, it is contemplated that anyor all of these hardware and software components could be embodiedexclusively in hardware, exclusively in software, exclusively infirmware or in some combination of hardware, firmware and/or software.Accordingly, while the above specification described example methods andarticles of manufacture, persons of ordinary skill in the art willreadily appreciate that the examples are not the only way to implementsuch methods and articles of manufacture. Therefore, although certainexample methods, apparatus and articles of manufacture have beendescribed herein, the scope of coverage of this patent is not limitedthereto. On the contrary, this patent covers all methods, apparatus andarticles of manufacture fairly falling within the scope of the appendedclaims either literally or under the doctrine of equivalents.

What is claimed is:
 1. A method, comprising: identifying a currentspeaker of a conference call; enabling, via a logic circuit, aparticipant in the conference call, other than the current speaker, torequest an adjustment of a volume of the current speaker, theparticipant different than the current speaker; and in response to arequest from the participant, adjusting, via the logic circuit, anamplification setting associated with the current speaker in apreference file associated with the participant.
 2. A method as definedin claim 1, wherein the determining of the identity of the currentspeaker is done from a record identifying the participants of theconference call.
 3. A method as defined in claim 2, further includingmaintaining the record of the participants of the conference call bytracking identification numbers associated with respective participantsas the corresponding participant joins the conference call.
 4. A methodas defined in claim 1, further including conveying an audio signal basedon the preference file associated with the participant to acommunication device of the participant.
 5. A method as defined in claim1, further including integrating the amplification setting into anaggregate audio signal to be conveyed to the participant.
 6. A method asdefined in claim 5, wherein the integrating of the amplification settingincludes performing a multiplication operation with the amplificationsetting and the incoming audio signal of the current speaker.
 7. Amethod as defined in claim 1, wherein the participant is a firstparticipant, and the adjusting of the amplification setting does notaffect a second one of the participants of the conference call, thesecond one of the participants different from the participant.
 8. Amethod as defined in claim 1, wherein the request from the participantis received via a web page having an input associated with theamplification setting of the current speaker.
 9. A method as defined inclaim 1, further including storing the amplification setting associatedwith the current speaker in the preference file for future conferencecalls.
 10. A method as defined in claim 1, further including sensing aninflection in a voice of the current speaker and visually conveying theinflection to the participant of the conference call.
 11. A method asdefined in claim 1, further including enabling the one other participantto adjust a universal amplification setting associated with theconference call.
 12. A tangible computer readable storage deviceincluding instructions that, when executed, cause a processor to performoperations comprising: identify a current speaker of a conference call;enable a participant of the conference call to request an adjustment ofa volume of the current speaker, the participant different than thecurrent speaker; and in response to a request from the otherparticipant, adjusting an amplification setting associated with thecurrent speaker in a preference file associated with the participant.13. The storage device as defined in claim 12, wherein the identifyingof the current speaker is done using a record identifying allparticipants of the conference call.
 14. The storage device as definedin claim 12, wherein the operations further include conveying an audiosignal based on the preference file associated with the participant to acommunication device of the participant.
 15. The storage device asdefined in claim 12, wherein the participant is a first participant, andthe adjusting of the amplification setting does not affect a secondparticipant of the conference call.
 16. The storage device as defined inclaim 12, wherein the request from the participant is received via a webpage having an input associated with the amplification setting of thecurrent speaker.
 17. The storage device as defined in claim 12, whereinthe operations further include enabling the participant to adjust auniversal amplification setting associated with the conference call. 18.An apparatus, comprising: memory including machine-readableinstructions; and a processor to execute the instructions to performoperations including: identifying a current speaker of a conferencecall; enabling a participant of the conference call to request anadjustment of a volume of the current speaker, the participant differentthan the current speaker; and in response to a request from participant,adjusting an amplification setting associated with the current speakerin a preference file associated with the participant.
 19. An apparatusas defined in claim 18, wherein the identifying of the identity of thecurrent speaker is done from a record of the participants of theconference call.
 20. An apparatus as defined in claim 18, wherein theparticipant is a first participant, and the adjusting of theamplification setting does not affect a second participant of theconference call.